Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: check healthcheck and heartbeat after ExApp container start #436

Merged
merged 1 commit into from
Oct 31, 2024

Conversation

bigcat88
Copy link
Member

After the previous PR(#430) which added stopping application containers feature when shutting down, as @andrey18106 correctly noted during our 1:1 conversation:

we cannot rely on the application inside the docker container to be ready to process the request at the moment the docker container is turned on.

This PR introduces handling of it by checking health-check and heartbeat.

Signed-off-by: bigcat88 <bigcat88@icloud.com>
@bigcat88 bigcat88 requested a review from andrey18106 October 31, 2024 16:23
Copy link
Collaborator

@andrey18106 andrey18106 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@bigcat88 bigcat88 merged commit 648fec3 into main Oct 31, 2024
26 of 30 checks passed
@bigcat88 bigcat88 deleted the fix/wait-after-container-start branch October 31, 2024 17:05
@bigcat88
Copy link
Member Author

/backport stable30

@bigcat88
Copy link
Member Author

/backport to stable30

Copy link

backportbot bot commented Oct 31, 2024

The backport to stable30 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable30
git pull origin stable30

# Create the new backport branch
git checkout -b backport/436/stable30

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 7360d998

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/436/stable30

Error: Failed to cherry pick commits: error: no cherry-pick or revert in progress
fatal: cherry-pick failed


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@bigcat88
Copy link
Member Author

/backport to stable29

Copy link

backportbot bot commented Oct 31, 2024

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/436/stable29

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 7360d998

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/436/stable29

Error: Failed to cherry pick commits: error: no cherry-pick or revert in progress
fatal: cherry-pick failed


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants